NTISthis.com

Evidence Guide: ICTWEB504 - Build a document using eXtensible markup language

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTWEB504 - Build a document using eXtensible markup language

What evidence can you provide to prove your understanding of each of the following citeria?

Plan the process

  1. Review the specified requirements
  2. Produce a plan to analyse the specified requirements
  3. Plan the design, and build, of valid XML documentation, allowing for iterative development
Review the specified requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Produce a plan to analyse the specified requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Plan the design, and build, of valid XML documentation, allowing for iterative development

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the specified requirements

  1. Determine and document the purpose, expectations and functionality of the XML document
  2. Determine the hardware, software and tools needed to design the document
  3. Determine the requirements for the document
  4. Determine the appropriate design methodologies, including using the software engineering life cycle
Determine and document the purpose, expectations and functionality of the XML document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the hardware, software and tools needed to design the document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the requirements for the document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the appropriate design methodologies, including using the software engineering life cycle

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design and develop the document

  1. Decide on document type definition (DTD), if required
  2. Define the required entities, elements and their attributes
  3. Produce the document, following the appropriate standards and declaring DTD, required entities, elements and their attributes, including associated graphics or sounds
Decide on document type definition (DTD), if required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define the required entities, elements and their attributes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Produce the document, following the appropriate standards and declaring DTD, required entities, elements and their attributes, including associated graphics or sounds

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test the document

  1. 4.1 Test the document off-line against the specifications, and confirm the document's validity
  2. Test, where appropriate, the document online against the specifications, and with a representative audience
  3. Analyse the test results and confirm the document’s validity
4.1 Test the document off-line against the specifications, and confirm the document's validity

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test, where appropriate, the document online against the specifications, and with a representative audience

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the test results and confirm the document’s validity

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Plan the process

1.1 Review the specified requirements

1.2 Produce a plan to analyse the specified requirements

1.3 Plan the design, and build, of valid XML documentation, allowing for iterative development

2. Analyse the specified requirements

2.1 Determine and document the purpose, expectations and functionality of the XML document

2.2 Determine the hardware, software and tools needed to design the document

2.3 Determine the requirements for the document

2.4 Determine the appropriate design methodologies, including using the software engineering life cycle

3. Design and develop the document

3.1 Decide on document type definition (DTD), if required

3.2 Define the required entities, elements and their attributes

3.3 Produce the document, following the appropriate standards and declaring DTD, required entities, elements and their attributes, including associated graphics or sounds

4. Test the document

4.1 Test the document off-line against the specifications, and confirm the document's validity

4.2 Test, where appropriate, the document online against the specifications, and with a representative audience

4.3 Analyse the test results and confirm the document’s validity

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Plan the process

1.1 Review the specified requirements

1.2 Produce a plan to analyse the specified requirements

1.3 Plan the design, and build, of valid XML documentation, allowing for iterative development

2. Analyse the specified requirements

2.1 Determine and document the purpose, expectations and functionality of the XML document

2.2 Determine the hardware, software and tools needed to design the document

2.3 Determine the requirements for the document

2.4 Determine the appropriate design methodologies, including using the software engineering life cycle

3. Design and develop the document

3.1 Decide on document type definition (DTD), if required

3.2 Define the required entities, elements and their attributes

3.3 Produce the document, following the appropriate standards and declaring DTD, required entities, elements and their attributes, including associated graphics or sounds

4. Test the document

4.1 Test the document off-line against the specifications, and confirm the document's validity

4.2 Test, where appropriate, the document online against the specifications, and with a representative audience

4.3 Analyse the test results and confirm the document’s validity

Evidence of the ability to:

review the specifications, and plan the design of an extensible markup language (XML) document

determine specific requirements

produce a valid XML document, following the appropriate standards

test an XML document

evaluate the test results.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain business process and information modelling

describe markup language

explain unified-modelling language

describe the hardware and software implications for XML programming

identify and summarise, the various standards that will impact on XML programming.